feat(ai-accounts): sort accounts by remaining quota - #929

What

The AI accounts list (/access/ai-accounts) could only be ordered by name. With many accounts, finding one that still has headroom meant reading every card.

Adds a sort control to the toolbar: by name (default), least quota left first, most quota left first.

This is the page I should have built #928 on. That PR added the same control to AI providers — I matched the nav label instead of the page you meant. This one is on AI accounts.

Design decisions worth reviewing

Ranked by the tightest quota the card actually shows. Scoping to the visible slots matters: antigravity reports both a 5h and a weekly bucket but the card renders only the 5h one. Ranking by a number the operator cannot see on the card reads as a broken sort. The rank therefore runs through resolveQuotaCardSlots — the same function that decides what the card displays.

Sorting pulls the full status snapshot once. This is the part that made a backend change look necessary, and then turned out not to need one:

The list loads status only for the accounts on the current page (visibleStatusScopeKey). That is right for rendering and useless for ordering — sorting a page by numbers only that page has just shuffles it. But GET /ai-accounts/status already returns every account when no auth_index filter is supplied, so the data was one parameterless call away. The order is applied in filteredFiles, before the slice into pages.

Nothing is fetched while sorting by name, so the default view is unaffected.

Unknown sorts last in both directions, keeping name order among themselves. Unknown is not empty and not full; floating it to the top of either direction would bury exactly what the operator opened the view to find. A failed snapshot leaves everything unranked, preserving name order rather than presenting a partial order as authoritative.

Preference and fetch state are module-scoped. AuthFilesPage.tsx (1210) and AuthFilesFilesTab.tsx (2579) are both frozen at their size baselines, and the gate only permits shrinking — threading this through as props was not available. The list and the toolbar control read the shared value independently. Neither file is touched by this change. The control lives in AuthFilesToolbarActions.tsx, which was itself extracted to keep the tab under the ratchet.

The control shows a spinner while the snapshot loads; without it the button looks inert for the duration of the request, which reads as broken.

No backend change

GET /ai-accounts/status with no filter already returns every account with its quota windows (ListStatus treats an empty filter as "all"). Verified in internal/management/aiaccountstatus/service.go.

Testing

7 new tests covering the rank calculation — including that antigravity's hidden weekly window is not used — and the shared preference (default, cross-instance sharing, persistence, unrecognised stored value).

tsc, oxlint, and all four structure gates pass. Full pages/auth-files suite green at 236 tests.

Not verified in a browser

I started the dev server and stopped at the login screen — I don't enter credentials. The control's appearance and the drop-down interaction are covered by tests but not by eye.

🤖 Generated with Claude Code